Package observations

The observations package represents the domain layer.

See:
Description

Interface Summary

DomainInterface

DomainInterface Is a simple interface meaning every object in this domain must have a unique name.

Class Summary

DomainObject	DomainObject Every object should inherit from this one.
Measurement	Measurement Represents something like 'bloodpressure 120 mm/Hg'.
NullPhenomenon	NullPhenomenon Special phenomenon without a name.
NullQuantity	NullQuantity Special quantity without amount and unit.
Observation	Observation Represents something like '10.10.04 bloodpressure high'.
Patient	Patient Represents a patient with all associated data and grants retrieval of phenomena, measurements and observations.
Phenomenon	Phenomenon Is a particular phenomenon like 'high' or 'obese'.
PhenomenonType	PhenomenonType Is a particular type of phenomenon, e.g.
Quantity	Quantity Represents a value such as 6 feet or 5 $.
QuantityRange	QuantityRange two quantities building a range from to.
Registrar	Registrar Manages saving an retreiving to/from memory.
Unit	Unit Simple unit like 'Euros' or 'Dollars'.

Exception Summary

OutOfRangeException

OutOfRangeException Is thrown when a value is out of preset valid range.

Package observations Description

The observations package represents the domain layer. It is the logical core of the system. vitalsFacade depends on it. This package contains many Fowler-patterns such as unit, measurement or knowledge-level. Most classes represent real-life-subjects from the domain (eg. patient). For further information see related documentation, please.

Related Documentation

For overviews, tutorials, examples, guides, and tool documentation, please see:

• UML-diagrams and usecase analysis
• Assignment: Fowler's article on application facades
• Index: tools and literature
• Metaphor: list of expressions
• DocCheck output

Since:

1.0 2004-09-17

See Also:

vitalsFacade